Configuration

Actually there should be no need for tweaking the configuration of the Job Log Explorer, because it has been designed to work independently from the language of the job log. But since it is impossible to test all languages and all date and time settings, it may happen, that the job log parser cannot successfully parse a job log.

For that case, the internally defined regular expressions can be overridden in file jobLogParser.properties. The file is created in the following directory when the Job Log Explorer is started for the first time:

[workspace]/.metadata/.plugins/biz.isphere.joblogexplorer/joblogparser/

By default that directory contains the example configuration file example_jobLogParser_vX.X.properties.

The file contains a description of each property. The properties are empty, in order to default to the standard regular expressions. Copy example_jobLogParser_vX.X.properties to jobLogParser.properties if you need to tweak a regular expression.

Note: Please notice that Java requires doubling back slashes when reading regular expressions from a file. See the example in example_jobLogParser_vX.X.properties.

Some regular expressions contains terms like &{MESSAGE_ID}. These strings, starting with an ampersand, are variable to make the regular expressions easier to read. They are replaced by their actual values before the expressions are compiled.

The following list shows the variables and their associated properties:

VariableProperty
JOB_NUMBERglobal.job.number
OBJECT_NAMEglobal.object.name
LICENSED_PROGRAMglobal.licensed.program
OS_RELEASEglobal.os.release
SPACESglobal.spaces
TIMEZONEglobal.timezone
SYSTEM_NAMEglobal.system.name
PAGE_NUMBER_LABELpage.number.label
PAGE_NUMBER_VALUEpage.number.value
PAGE_DATEpage.date
PAGE_TIMEpage.time
HEADER_ATTRIBUTE_NAMEheader.attribute.name
HEADER_ATTRIBUTE_VALUEheader.attribute.value
MESSAGE_IDmessage.id
MESSAGE_TYPEmessage.type
MESSAGE_SEVERITYmessage.severity
MESSAGE_DATEmessage.date
MESSAGE_TIMEmessage.time
MESSAGE_CONTINUATION_LINE_INDENTIONmessage.continuation.line.indention

The table below shows the keys that can be used to specify complete regular expressions with or without variables:

PropertyDescription
regex.startOfPageIdentifies the start of a page. Retrieves the system name and page number.
regex.headerAttributeParses the page header. Retrieves the job name and job description.
regex.messageFirstLineParses the message attributes, such as ID, type, description, from the first line of the message.
regex.messageContinuationLineParses additional message attributes, such as message text, program name, library name and statement number, from the message continuation lines.